An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hello, Our app has been in "Waiting for Review" status for more than a week, and our previous submission also took over a week to be reviewed. This delay is affecting our planned release schedule. App details: App name: Nhật Luân Kiếm App ID: 6777269196 We'd really appreciate any guidance on the current review timeline, or whether there is anything on our side we can do to help move the review forward. We're happy to provide any additional information if needed. Thank you very much for your time and support. Best regards.

I would like to start up by saying how much I appreciate all the Apple employees, developers, reviewers, and testers for the incredible job they do. The number of apps that come through on a daily basis is probably astronomical. All that said, I am a bit curious as to why I was able to put three different apps into review in the last 24 hours, and as of now, they have all 3 been processed and released. In the meantime, I have an app that is still in Waiting for Review. This app has some core functionality involved as well as some more simple text changes. I’d to hear from Apple at the least, what is the hold up. If there is a code issue, tell me. If there is a behavior or UI issue, tell me. One of these changes was time critical for releasing in June. Thanks for letting me vent. I just hope the App Review folks look into it.

How can Apple deny my appeal and not approve my app for tobacco when multiple apps like these are on the store?

I have finished a new app that integrates Apple hosted background asset. I have tested and confirm that the assets are downloaded both locally and with a TestFlight build. App review is not able to access the background assets. I can see that the assets are updated with status "accepted". But app review is running into error "A server with the specified hostname could not be found.". These are Apple Hosted Assets. Did I miss any configuration?

My app (RunWeather) is live on the App Store, but its two auto-renewable subscriptions have never reached Approved, so the StoreKit paywall returns no products and users can't subscribe. Subscriptions: com.iustinn.runweather.pro.monthly com.iustinn.runweather.pro.annual Both show "Pending Binary Approval". The English (U.S.) localization on each is stuck in "Rejected", and App Store Connect won't let me edit or delete that localization (the fields are locked), so I can't correct the copy and resubmit. I never received a clear reason for the localization rejection. History: each time I submitted a build with these subscriptions, the build was rejected for an unrelated reason; I resubmitted, the build was eventually approved, but the subscriptions stayed behind in this stuck state. I also created duplicate subscription products (…monthly2/3/4, …annual2/3/4) as a workaround; those just sit in "In Review" indefinitely. What I've tried: Editing / deleting the Rejected U.S. localization -> blocked, fields locked. Re-submitting builds -> app approved, subscriptions not. Questions: How do you unstick a subscription whose Rejected localization can't be edited or deleted? Is an App Review support ticket the only path to reset it? For "Pending Binary Approval" subscriptions, does attaching them to a NEW app version (reusing the existing build, no new binary) and submitting force them back through review? Has anyone cleared this exact locked-localization state another way? I've also opened an App Review case. Posting here in case someone hit the same locked-localization state. Thanks.

Hello everyone, I’m looking for advice from developers who have been through a Guideline 4.3(a) (Design – Spam) rejection. Our game was rejected under Guideline 4.3(a). We genuinely believe it is an original Unity project that we developed from scratch. Instead of immediately submitting a new build, we replied through the Resolution Center with extensive supporting documentation, including: Figma design history Unity project structure Development timeline Original UI/UX workflow Comparisons explaining how our game differs from similar titles We also submitted a formal appeal to the App Review Board and later sent a polite follow-up message. It has now been 12 days since our last message, and we still haven’t received any response from Apple. I’m not asking whether our rejection was correct or incorrect. I’m simply trying to understand the review process. For developers who have experienced this: Is waiting 10–14+ days after submitting evidence normal? Did Apple eventually respond? Did they continue the conversation in the Resolution Center, or did they ask for a new build? Is there anything else we should do besides waiting? Any experiences or advice would be greatly appreciated. Thank you!

Hello Apple App Review Team, I’m an independent developer and I’m hoping someone can point me in the right direction or let me know if this is simply an unusually long review. My app, PM Quest Prep, has already been approved and is currently available on the App Store. The only thing preventing my full launch is that every subscription-related item has remained in “Waiting for Review” for over two weeks. At this point I’m not sure if everything is simply waiting in the normal review queue or if something may have become stuck. App Information App Name: PM Quest Prep App Apple ID: 6772685314 Bundle ID: com.questforge.pmquestprep SKU: PQP-IOS-001 ⸻ Subscription Group PM Quest Prep Pro Subscription Group ID: 22130056 Status: Waiting for Review ⸻ Subscriptions PM Quest Prep Pro Monthly Apple ID: 6776040575 Product ID: pm_quest_prep_monthly Status: Waiting for Review PM Quest Prep Pro Quarterly Apple ID: 6776043289 Product ID: pm_quest_prep_quarterly Status: Waiting for Review PM Quest Prep Pro Yearly Apple ID: 6776060042 Product ID: pm_quest_prep_yearly Status: Waiting for Review ⸻ Additional Items Waiting for Review Along with the subscriptions themselves, the following items are also still waiting: Subscription Group Subscription Localizations Subscription Display Information Subscription Promotional Images Promotional Image Assets Everything associated with the subscription group appears to be waiting together. ⸻ What I’ve Already Verified Before posting here, I wanted to make sure I wasn’t overlooking something. I’ve confirmed the following: The app itself has already been approved and is live on the App Store. Banking information has been completed. Tax information has been completed. The Paid Applications Agreement has been accepted. Pricing has been configured. Availability has been configured. Subscription metadata has been completed. Localizations have been completed. Promotional images have been uploaded. StoreKit implementation has been tested. App Store Connect is not showing any warnings, errors, or requests for additional information. From everything I can see, there isn’t anything left for me to complete. ⸻ Apple Developer Support I also opened a support case before posting here. Developer Support Case ID: 102919993053 Support emails were sent on: June 19, 2026 June 26, 2026 I’m still waiting for the subscriptions and all related assets to move beyond Waiting for Review. ⸻ Why I’m Asking I’ve spent the last several months building PM Quest Prep, and it’s exciting to finally have the app available on the App Store. Unfortunately, users can’t subscribe to the Pro features until these subscription reviews are completed, so the app can’t fully launch as intended. I’m completely understanding if review times are simply longer right now—I just want to make sure there isn’t an issue on my account or something I’ve unintentionally missed. If an Apple App Review engineer happens to see this post, would someone be willing to verify whether everything is still progressing normally or if there’s anything preventing these subscriptions from being reviewed? If you need any additional information from me, I’ll be happy to provide it immediately. Thank you very much for your time, and thank you to the App Review team for everything you do. Best regards, Dustin Harris Developer of PM Quest Prep

Hi everyone, and hopefully Apple Staff, I am looking for some advice or assistance regarding an unusually long App Review delay for our game. On June 23 (Tuesday), we submitted a comprehensive appeal and build (v1.0.5). It has been 7 days and our app is still not in the "In Review" state. This unexpected delay is severely impacting our marketing schedule in Turkey. We have pre-launch campaigns, offline events, and schedules with about 30 local KOLs that are being continuously delayed, causing significant financial and operational impact. I have already submitted an Expedited Review Request, but I haven't received any updates yet. Has anyone else experienced similar delays recently after an appeal? Are there any Apple representatives here who could kindly take a look at our Submission ID? Any advice on how to proceed would be greatly appreciated. Here are the details of our submission: App Name: Era Online: Şeref Savaşı App ID: 6773240689 Bundle ID: com.ark.xhmzxqteq.ios Submission ID: d19cb33a-b179-4f82-85e7-4acc77f46968 Thank you so much for your time.

Hi everyone, and hopefully Apple Staff, I am looking for some advice or assistance regarding an unusually long App Review delay for our game. Here are the details of our submission: App Name: Era Online: Şeref Savaşı App ID: 6773240689 Bundle ID: com.ark.xhmzxqteq.ios Submission ID: d19cb33a-b179-4f82-85e7-4acc77f46968 Background: Our app was previously rejected under guidelines 2.1(a) - App Completeness and 4.3(a) - Spam. On June 23 (Tuesday), we submitted a comprehensive appeal and a new build (v1.0.5): For 2.1(a): We completely fixed the occasional iPad crash issue and thoroughly tested the new build. For 4.3(a): We provided extensive legal documentation proving we hold the exclusive publishing rights for this game in Turkey. We also demonstrated that our app is a highly customized, exclusive version for the Turkish market, featuring a 300,000-word localization, local voice acting, unique IAPs priced in Turkish Lira, dedicated servers in Ankara, and exclusive in-game classes. The Issue: It has been a week, and our app is still not in the "Waiting For Review" state. This unexpected delay is severely impacting our marketing schedule in Turkey. We have pre-launch campaigns, offline events, and schedules with about 30 local KOLs that are being continuously delayed, causing significant financial and operational impact. I have already submitted an Expedited Review Request, but I haven't received any updates yet. Has anyone else experienced similar delays recently after an appeal? Are there any Apple representatives here who could kindly take a look at our Submission ID? Any advice on how to proceed would be greatly appreciated. Thank you so much for your time.

Repeated "Invalid Binary" rejections with no error code or explanation — 9 builds, no guidance I'm building a simple React Native/Expo app — essentially a link hub pointing to pages on our website (booking, events, Facebook group, etc.). Nothing exotic: no special entitlements, no background processes, no third-party SDKs beyond standard Expo modules. I'm now on build 1.0.0 (9) and every single submission has come back as "Invalid Binary" with zero explanation — no ITMS error code in App Store Connect, and no rejection email ever arrives (confirmed by checking spam and verifying my Apple ID email is correct and monitored). What I've already ruled out / fixed along the way: Upgraded Expo SDK to match the latest patch version Fixed a corrupted splash screen asset (was a JPG mislabeled as PNG) Populated the submit section in eas.json with correct Apple ID, ASC App ID, and bundle identifier Confirmed Apple ID email matches across Apple Developer account and EAS config Accepted the most recent Developer Program License Agreement update Excluded visionOS support explicitly in app.json Verified app icon is a proper 1024x1024 square PNG with no transparency I opened a support case (#102916564146) and was told it would be escalated to App Review. That was over two weeks ago with no follow-up. Has anyone dealt with a persistent silent "Invalid Binary" loop like this? Specifically interested in whether there's a way to request the actual ITMS error code when App Store Connect and email both come up empty.

Our Flutter app has been rejected by App Review 4 times with this description: "Login screen cleared the email and password fields when we attempted to enter the demo account details, preventing us from logging in." Review environment: Device: iPad Air 11-inch (M3) OS: iPadOS 26.4.2 Flutter version: 3.41.4 State management: GetX We cannot reproduce this on: Real iPhone (iOS 18.x) — works fine iPad simulator (iPadOS 26.3.1) — works fine Our TextEditingControllers are created inside a GetX controller, not inside build(), so they survive widget rebuilds. Questions: Has anyone seen text fields clearing or not retaining input specifically on iPad with iPadOS 26? Are there any known Flutter issues with text input on iPadOS 26 that could cause this? Is there anything different about how iPad handles text input vs iPhone that we should be aware of? Any help appreciated — this is blocking our App Store approval.

I have submitted an application review on the 25th of June and yet to change status from waiting for review, documentation states up to 48 hours wait time but we’re now getting towards 4 days, I’ve tried submitting a case and had no response at all, tried calling the support line to be told they are seperate from the general support phone line, is it possible to get some form of update on how much longer I need to wait as the app can’t go live till approved

Hi, I was wondering about Apple's review queues. I have an app that in waiting for review for almost a week now but review time trackers claim average waiting times less than a day: https://www.runway.team/appreviewtimes My previous experience is also quite inconsistent, can you please shed some light on how things work internally? In this time I have done some improvements on the app that I was considering for the next update, should I cancel and re-submit?

Hello App Review Team, I'm hoping someone can take a manual look or point me in the right direction. The iOS build of my app has been sitting in "Waiting for Review" with no status change, while the macOS and tvOS builds of the exact same version have already been reviewed and released. App: VixioTV - IPTV & M3U Player App ID: 6763137740 Platform: iOS (iPhone/iPad) Current status: Waiting for Review Most recent submission: [June 24, 2026] Time in queue: ~24 days with no status change Related case IDs: [your expedited review / Developer Support case numbers] Context I'd like to share proactively: This is an update to an app that is ALREADY LIVE on the App Store (current iOS version 1.2). It is not a new app. The macOS and tvOS versions of this same update have already passed review and are live — only the iOS build is stuck. VixioTV is a bring-your-own-content player: it provides no broadcasts or content of its own. Users connect their own IPTV subscription (API credentials or an M3U URL). There is no registration, subscription, or content sale inside the app. I have submitted expedited review requests and contacted Developer Support, but I've only received generic/automated replies with no change in status. I would really appreciate it if someone could: Confirm whether there is any issue with the build, metadata, agreements, or account that requires action on my side. Indicate whether this is queue congestion or a submission-specific hold. If possible, escalate or trigger a manual review. Thank you very much for your help. Selcuk Kaymaz

Hi, I added two new auto-renewable subscriptions to an existing subscription group: 50GB Monthly 50GB Yearly The other subscriptions in the same group (200GB and 500GB monthly/yearly) have already been approved. However, these two new subscriptions have remained "In Review" for over 3 days without any updates. Is this normal, or could the review be stuck? Has anyone experienced the same issue? Thanks!

Hi everyone, We're experiencing an unusually long App Review delay for our tvOS application and wanted to check if anyone else is seeing the same behaviour or has any suggestions. App Details Platform: tvOS Xcode Version: 26.4.1 Submission Type: App Update Distribution: App Store Status: In Review Issue We submitted an app update last week, and it remained in the "In Review" state for approximately one week with no updates. Since there was no progress, we rejected that submission, uploaded a new build, and submitted it again. The new build has now also been "In Review" for the last 5 days. Apple has not rejected the app or provided any review notes or requests for additional information. The status simply remains "In Review". What we've tried Submitted an Expedited Review Request. Contacted Apple using the App Review "Contact Us" option. We have not received any response to either request. Since there is no rejection or feedback, we don't have any indication that there is an issue with the app itself. Questions Is anyone else currently experiencing unusually long review times for tvOS apps? Is this likely to be an App Review backlog or a known issue on Apple's side? Has anyone had success getting a response through App Review support or Developer Support in a similar situation? Is there anything else we can do besides waiting? Any insights or recent experiences would be greatly appreciated. Thank you!

I'm building a custom keyboard extension that offers voice dictation. Because keyboard extensions are constrained (memory cap ~30–48 MB, restricted audio session access), I delegate recording to my container app: User in a host app (e.g., Safari) taps the mic in my keyboard extension. The keyboard calls extensionContext.open(URL("myapp://dictation")) to launch the container app. The container app records audio via AVAudioEngine + SFSpeechRecognizer, writes the final transcript to the App Group, and signals completion via a Darwin notification. 4. The user is expected to be returned to the original host app (Safari) automatically so they can keep typing. The problem (step 4): On iOS 26.4 I can no longer identify which app was the host. Every previously-known path returns nil for the keyboard extension's host: parent.value(forKey: "_hostBundleID") → returns the literal string parent.value(forKey: "_hostApplicationBundleIdentifier") → returns NSNull xpc_connection_copy_bundle_id on the underlying XPC connection (via PKService.defaultService.personalities[…]) → returns NULL NSXPCConnection.processBundleIdentifier on extensionContext._extensionHostProxy._connection → returns nil proc_pidpath(hostPID, …) → EPERM from the keyboard sandbox LSApplicationWorkspace.frontmostApplication → selector unavailable from the extension RBSProcessHandle.handleForIdentifier:error: → returns an RBSServiceErrorDomain error Without the host's bundle ID, the container app has no way to call LSApplicationWorkspace.openApplicationWithBundleID: (the technique that worked on iOS 25 and earlier). UIApplication.suspend() correctly sends the container to background, but iOS treats us as a "fresh launch" — it returns the user to the Home Screen instead of Safari, because the container app was launched by an extension, not directly by Safari. KeyboardKit's maintainer reached the same conclusion (issue #1014) and shipped 10.4 without the feature. My questions: Is there a public, App-Store-safe API in iOS 26+ for a custom keyboard extension to identify its host application, or for the container app (launched via the extension's openURL) to identify which app initially hosted the extension that opened it? UIOpenURLContext.options.sourceApplication reports the extension's own container, not the actual host. 2. Is there a public mechanism for "return to source app" when the container app was launched by an extension's openURL? Equivalent to the ← Source affordance iOS shows for normal inter-app openURL, but triggered programmatically by the launched app. 3. Some popular keyboards (e.g., 微信输入法 / WeChat Keyboard) still appear to round-trip through their container app on iOS 26.4 and return the user to the original host — including the iOS ← WeChat back affordance in the host's status bar afterward. What's the recommended approach to achieve this? If it requires a specific scene-activation flow, NSUserActivity pattern, or extension-context configuration, please point at the relevant docs. 4. If there is no public path today, is FB22247647 (or a related radar) the right place to track this? Should developers in this position migrate to in-extension audio capture (which has its own significant constraints in keyboard extensions)? I'd much rather not rely on private APIs. Concrete guidance — or even an acknowledgment of which direction Apple intends — would help thousands of custom-keyboard developers who currently have a degraded voice-input experience on iOS 26.4+. Tested on iPhone 12 Pro Max running iOS 26.4.2 (build 23E261), Xcode 26.x, Swift 5. Thanks!

Details: I'm looking for clarification on how Guideline 1.4.3 is applied to tobacco related apps. My app, The Leaf Cellar, was rejected under 1.4.3 with the reasoning that its "current concept is not appropriate" because it relates to tobacco. The app is a private inventory manager. It has no store, no purchasing, no vendor or affiliate links, no discovery feed, and no content directed at encouraging or using tobacco. its only function is personal record-keeping (logging inventory you already own, aging dates, humidity readings). A 21+ age gate is enforced on launch. What I'm trying to understand is the consistency of the guideline, because functionally identical apps are currently live on the store and receiving updates (which means apple must approve the submitted updates.) Existing Apps (not being enforced by 1.4.3): "My Humidor – Cigar Journal": [https://apps.apple.com/us/app/my-humidor-cigar-journal/id6639582700] "Humidor Journal Pro": [https://apps.apple.com/us/app/humidor-journal-pro/id6751737114] Questions: Is there a specific feature or distinction that separates an approvable cigar-journal app from one rejected under 1.4.3 as a "concept"? If apps in this category are already approved, what's the correct path to have an inconsistent rejection reviewed beyond the standard Resolution Center reply? I have already submitted to the App Review Board.

Hello, my app id 6756081224 Waiting for Review 10 day ago Help me please

Hi all, My first app submission appears to be stalled (16+ days) and I’m completely in the dark as to what is going on. Apple ID: 6776835006 Submission ID: 236039a0-1668-448a-aae6-486d52e6c5b9 Timeline: Ready for Review: Jun 10, 2026 at 3:22 AM Waiting for Review: Jun 10, 2026 at 3:23 AM In Review: Jun 15, 2026 at 5:05 PM Current status: still In Review as of Jun 26, 2026 I have also submitted 2 support cases that are past 48 hour SLA and an expedited review request, but I haven’t received a response yet. Our TestFlight external build has also been stuck in Waiting for Review for 5+ days now. There are no visible unresolved issues, App Review messages, or missing compliance warnings in App Store Connect. Review notes and demo/testing information are provided. Thank you.